docs(artifacts): document Azure storage handler #207
Conversation
|
|
||
| For an example of tracking reference files in GCP, see the [Guide to Tracking Artifacts by Reference](https://wandb.ai/stacey/artifacts/reports/Tracking-Artifacts-by-Reference--Vmlldzo1NDMwOTE). | ||
|
|
||
| The following describes how to construct reference artifacts and how to best incorporate them into your workflows. |
There was a problem hiding this comment.
@ngrayluna Hey Noah! One thing I was thinking - would it make sense to add a box that specifies that Azure has been newly added? Similar to how we have 'warning' blocks, would there be a similar one to add for a new feature to call attention that Reference Artifacts in Azure are now available? We will surface this elsewhere as well but was wondering if there's a place in this doc to call this out as well..
There was a problem hiding this comment.
Sadly, it is considered a 'bad practice' to include text, blocks etc. that is 'dated' in tech docs . :/
There was a problem hiding this comment.
Gotcha makes sense, I had been thinking of something like this but it sounds like we are working to remove similar blocks / deprecate going forward.
szymon-piechowicz-wandb
force-pushed
the
szymon/artifacts_azure
branch
from
fc41141 to
25f46f1
Compare
Description
Documented new functionality added in wandb/wandb#5317.
Ticket
WB-13498
Checklist
Check if your PR fulfills the following requirements. Put an
Xin the boxes that apply.yarn start. My changes did not break the local preview.yarn docusaurus build) was run locally and successfully without errors or warnings.maininto my feature branch before submitting this PR.